Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 14, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^24.10.1^24.10.7 age confidence
@vitest/coverage-v8 (source) ^4.0.15^4.0.17 age confidence
esbuild ^0.27.0^0.27.2 age confidence
eslint (source) ^9.39.1^9.39.2 age confidence
eslint-config-unjs ^0.5.0^0.6.2 age confidence
miniflare (source) ^4.20251128.0^4.20260111.0 age confidence
obuild ^0.4.4^0.4.14 age confidence
pnpm (source) 10.24.010.28.0 age confidence
rollup (source) ^4.53.3^4.55.1 age confidence
vite (source) ^7.2.6^7.3.1 age confidence
vitest (source) ^4.0.15^4.0.17 age confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v4.0.17

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.16

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.27.2

Compare Source

  • Allow import path specifiers starting with #/ (#​4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#​4357, #​4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    
    /* Old output (with --target=chrome110) */
    main {
      mask: url(x.png) center/5rem no-repeat;
    }
    
    /* New output (with --target=chrome110) */
    main {
      -webkit-mask: url(x.png) center/5rem no-repeat;
      mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#​4176, #​4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }
    
    // Old output (with --minify)
    switch(x){case 0:foo();break;case 1:default:bar()}
    
    // New output (with --minify)
    x===0?foo():bar();
  • Forbid using declarations inside switch clauses (#​4323)

    This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced using declarations. These were previously allowed inside case and default clauses in switch statements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.

    Here is an example of code that is no longer allowed:

    switch (mode) {
      case 'read':
        using readLock = db.read()
        return readAll(readLock)
    
      case 'write':
        using writeLock = db.write()
        return writeAll(writeLock)
    }

    That code will now have to be modified to look like this instead (note the additional { and } block statements around each case body):

    switch (mode) {
      case 'read': {
        using readLock = db.read()
        return readAll(readLock)
      }
      case 'write': {
        using writeLock = db.write()
        return writeAll(writeLock)
      }
    }

    This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).

v0.27.1

Compare Source

  • Fix bundler bug with var nested inside if (#​4348)

    This release fixes a bug with the bundler that happens when importing an ES module using require (which causes it to be wrapped) and there's a top-level var inside an if statement without being wrapped in a { ... } block (and a few other conditions). The bundling transform needed to hoist these var declarations outside of the lazy ES module wrapper for correctness. See the issue for details.

  • Fix minifier bug with for inside try inside label (#​4351)

    This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the try statement to address a problem with transforming labeled for await loops to avoid the await (the transformation involves converting the for await loop into a for loop and wrapping it in a try statement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply to for loops that esbuild itself generates internally as part of the for await transform. Here is an example of some affected code:

    // Original code
    d: {
      e: {
        try {
          while (1) { break d }
        } catch { break e; }
      }
    }
    
    // Old output (with --minify)
    a:try{e:for(;;)break a}catch{break e}
    
    // New output (with --minify)
    a:e:try{for(;;)break a}catch{break e}
  • Inline IIFEs containing a single expression (#​4354)

    Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single return statement. Now it should also work if the body contains a single expression statement instead:

    // Original code
    const foo = () => {
      const cb = () => {
        console.log(x())
      }
      return cb()
    }
    
    // Old output (with --minify)
    const foo=()=>(()=>{console.log(x())})();
    
    // New output (with --minify)
    const foo=()=>{console.log(x())};
  • The minifier now strips empty finally clauses (#​4353)

    This improvement means that finally clauses containing dead code can potentially cause the associated try statement to be removed from the output entirely in minified builds:

    // Original code
    function foo(callback) {
      if (DEBUG) stack.push(callback.name);
      try {
        callback();
      } finally {
        if (DEBUG) stack.pop();
      }
    }
    
    // Old output (with --minify --define:DEBUG=false)
    function foo(a){try{a()}finally{}}
    
    // New output (with --minify --define:DEBUG=false)
    function foo(a){a()}
  • Allow tree-shaking of the Symbol constructor

    With this release, calling Symbol is now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:

    // Original code
    const a = Symbol('foo')
    const b = Symbol(bar)
    
    // Old output (with --tree-shaking=true)
    const a = Symbol("foo");
    const b = Symbol(bar);
    
    // New output (with --tree-shaking=true)
    const b = Symbol(bar);
eslint/eslint (eslint)

v9.39.2

Compare Source

unjs/eslint-config (eslint-config-unjs)

v0.6.2

Compare Source

compare changes

🩹 Fixes
  • Disable array immutation rules for now (3cde73a)
❤️ Contributors

v0.6.1

Compare Source

compare changes

💅 Refactors
  • Migrate to @eslint/markdown (2f92a53)
  • Update default rules (84cdbad)
📦 Build
🏡 Chore
❤️ Contributors

v0.6.0

Compare Source

compare changes

💅 Refactors
  • Migrate to @eslint/markdown (2f92a53)
📦 Build
🏡 Chore
❤️ Contributors
cloudflare/workers-sdk (miniflare)

v4.20260111.0

Compare Source

Patch Changes
  • #​11494 ed60c4f Thanks @​jalmonter! - Fix scheduled trigger warning showing undefined port

    When running wrangler dev with a worker that has cron triggers, the warning message displayed an invalid URL like curl "http://localhost:undefined/cdn-cgi/handler/scheduled" because the port wasn't yet determined when the warning was logged.

    Moved the warning to after the proxy server is fully ready, where the actual public URL and port are known.

  • #​11831 faa5753 Thanks @​dependabot! - chore: update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260107.1 1.20260108.0
  • #​11844 e574ef3 Thanks @​dependabot! - chore: update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260108.0 1.20260109.0
  • #​11872 b6148ed Thanks @​dependabot! - chore: update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260109.0 1.20260111.0
  • #​11816 fc96e5f Thanks @​dario-piotrowicz! - Bump sharp dependency (from 0.33.5 to 0.34.5)

v4.20260107.0

Compare Source

Patch Changes
  • #​11822 97e67b9 Thanks @​dependabot! - chore: update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260103.0 1.20260107.1

v4.20260103.0

Compare Source

Minor Changes
  • #​11648 eac5cf7 Thanks @​pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:

    • getOutput(): Returns the output of the successfully completed Workflow instance.
    • getError(): Returns the error information of the errored Workflow instance.

    Example:

    // First wait for the workflow instance to complete:
    await expect(
    	instance.waitForStatus({ status: "complete" })
    ).resolves.not.toThrow();
    
    // Then, get its output
    const output = await instance.getOutput();
    
    // Or for errored workflow instances, get their error:
    await expect(
    	instance.waitForStatus({ status: "errored" })
    ).resolves.not.toThrow();
    const error = await instance.getError();
Patch Changes
  • #​11714 65d1850 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251217.0 1.20251219.0
  • #​11732 1615fce Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251219.0 1.20251221.0
  • #​11748 b2769bf Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251221.0 1.20251223.0
  • #​11791 554a4df Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251223.0 1.20260103.0
  • #​11642 8eede3f Thanks @​petebacondarwin! - Fix intermittent "Fetch failed" errors in Miniflare tests on Windows

    Miniflare tests would occasionally fail with "Fetch failed" errors (particularly on Windows CI runners) due to race conditions between undici's Keep-Alive mechanism and the Miniflare server closing idle connections. Miniflare now configures the Dispatcher to prevent connection reuse and eliminate these race condition errors.

  • #​11493 6a05b1c Thanks @​GameRoMan! - Update zod from 3.22.3 to 3.25.76

v4.20251217.0

Compare Source

Patch Changes
  • #​11679 ae1ad22 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251213.0 1.20251217.0
  • #​11663 737c0f4 Thanks @​NuroDev! - Fix Durable Object RPC calls from Node.js blocking the event loop, preventing Promise.race() and timeouts from working correctly.

    Previously, RPC calls from Node.js to Durable Objects would block the Node.js event loop, causing Promise.race() with timeouts to never resolve. This fix ensures that RPC calls properly yield control back to the event loop, allowing concurrent operations and timeouts to work as expected.

v4.20251213.0

Compare Source

Patch Changes
  • #​11596 5d085fb Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251210.0 1.20251211.0
  • #​11622 b75b710 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251211.0 1.20251212.0
  • #​11640 1e9be12 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251212.0 1.20251213.0

v4.20251210.0

Compare Source

Patch Changes
  • #​11552 31c162a Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251202.0 1.20251205.0
  • #​11583 bd5f087 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251205.0 1.20251209.0
  • #​11584 c6dd86f Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251209.0 1.20251210.0

v4.20251202.1

Compare Source

Patch Changes

v4.20251202.0

Compare Source

Patch Changes
  • #​11495 59534ba Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251128.0 1.20251202.0
unjs/obuild (obuild)

v0.4.14

Compare Source

compare changes

🏡 Chore
  • Update rolldown to 1.0.0-beta.59 (51bd7d2)
❤️ Contributors

v0.4.13

Compare Source

compare changes

🩹 Fixes
  • rolldown: Revert includeDependenciesRecursively (7325ddd)
❤️ Contributors

v0.4.12

Compare Source

compare changes

🩹 Fixes
  • rolldown: Enable includeDependenciesRecursively (6974fb5)
  • bundle: Avoid recursion on resolveDeps (2bba5b9)
❤️ Contributors

v0.4.11

Compare Source

compare changes

🏡 Chore
❤️ Contributors

v0.4.10

Compare Source

compare changes

🏡 Chore

v0.4.9

Compare Source

compare changes

🏡 Chore
❤️ Contributors

v0.4.8

Compare Source

compare changes

📖 Documentation
  • Add c12 to "currently used" section (#​66)
🏡 Chore
🤖 CI
  • Bump actions checkout (#​64)
❤️ Contributors

v0.4.7

Compare Source

compare changes

💅 Refactors
  • rolldown: Use dist/_chunks for chunks (c1c8877)
❤️ Contributors

v0.4.6

Compare Source

compare changes

🚀 Enhancements
  • rolldown: Use dist/_libs for bundled dependencies (ec8c3fe)
❤️ Contributors

v0.4.5

Compare Source

compare changes

🩹 Fixes
  • rolldown: Default platform to node (439b03a)
🏡 Chore
❤️ Contributors
pnpm/pnpm (pnpm)

v10.28.0

Compare Source

v10.27.0

Compare Source

v10.26.2: pnpm 10.26.2

Compare Source

Patch Changes

  • Improve error message when a package version exists but does not meet the minimumReleaseAge constraint. The error now clearly states that the version exists and shows a human-readable time since release (e.g., "released 6 hours ago") #​10307.

  • Fix installation of Git dependencies using annotated tags #​10335.

    Previously, pnpm would store the annotated tag object's SHA in the lockfile instead of the actual commit SHA. This caused ERR_PNPM_GIT_CHECKOUT_FAILED errors because the checked-out commit hash didn't match the stored tag object hash.

  • Binaries of runtime engines (Node.js, Deno, Bun) are written to node_modules/.bin before lifecycle scripts (install, postinstall, prepare) are executed #​10244.

  • Try to avoid making network calls with preferOffline #​10334.

Platinum Sponsors

Bit

Gold Sponsors

Discord CodeRabbit Workleap
Stackblitz Vite

v10.26.1: pnpm 10.26.1

Compare Source

Patch Changes

  • Don't fail on pnpm add, when blockExoticSubdeps is set to true #​10324.
  • Always resolve git references to full commits and ensure HEAD points to the commit after checkout #​10310.

Platinum Sponsors

Bit

Gold Sponsors

Discord CodeRabbit Workleap
Stackblitz Vite

v10.26.0

Compare Source

v10.25.0

Compare Source

rollup/rollup (rollup)

v4.55.1

Compare Source

2026-01-05

Bug Fixes
  • Fix artifact reference for OpenBSD (#​6231)
Pull Requests

v4.54.0

Compare Source

2025-12-20

Features
  • Enable tree-shaking for Symbol.hasInstance, Symbol.dispose and Symbol.asyncDispose properties if unused (#​6046)
Bug Fixes
  • Ensure that well-known-Symbol-valued properties are not tree-shaken except in select cases (#​6046)
  • Ensure namespace properties are included when referenced only from a try-catch (#​6216)
Pull Requests

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 14cd212 to d8a8f4d Compare November 20, 2025 22:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from baa65e4 to efc45ca Compare November 27, 2025 19:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from b9ff9fb to 4fdec0f Compare December 3, 2025 05:10
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update all non-major dependencies - autoclosed Dec 3, 2025
@renovate renovate bot closed this Dec 3, 2025
@renovate renovate bot deleted the renovate/all-minor-patch branch December 3, 2025 10:39
@renovate renovate bot changed the title chore(deps): update all non-major dependencies - autoclosed chore(deps): update all non-major dependencies Dec 7, 2025
@renovate renovate bot reopened this Dec 7, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from b7de22b to 32a0b83 Compare December 11, 2025 11:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 7afb5e2 to 7ecff38 Compare December 19, 2025 03:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 1e64324 to 63a5fed Compare December 23, 2025 14:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 6294035 to 3b900da Compare January 6, 2026 22:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from ef7b1c0 to 5626bde Compare January 12, 2026 14:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5626bde to fd3cfbb Compare January 13, 2026 12:44
@pi0 pi0 merged commit 408c649 into main Jan 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants